Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Actually use the compile --outputPath option if the user provides one #2432

Conversation

majcosta
Copy link
Contributor

It was just not being used, defaulting to the parent of installPath. it still does, if the user does not specify a directory using --outputPath

@majcosta majcosta changed the title Actually use the -o option if the user provides one Actually use the compile --outputPath option if the user provides one Oct 26, 2023
It was just not being used, defaulting to the parent of installPath. it
still does, if the user does not specify a directory using --outputPath
@EzioTheDeadPoet
Copy link
Contributor

I will test it in the preview branch and see to include it in the changes I have planned to work on today.

@EzioTheDeadPoet EzioTheDeadPoet changed the base branch from main to pr_use_outputpath November 2, 2023 13:25
@EzioTheDeadPoet EzioTheDeadPoet merged commit 2adcf45 into wabbajack-tools:pr_use_outputpath Nov 2, 2023
1 of 4 checks passed
@majcosta majcosta deleted the pr_use_outputpath branch November 2, 2023 14:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants